Skip to content

Conversation

@tylersmalley
Copy link
Contributor

@tylersmalley tylersmalley commented Jan 15, 2019

Follow-up to #28497

Since elastic/elasticsearch#37285 has been merged, it's
apparent there are a couple more places we need to specify include_type_name
as a stop-gap until #23650 is completed

@tylersmalley tylersmalley added the Team:Operations Kibana-Operations Team label Jan 15, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

@elasticmachine

This comment has been minimized.

@elasticmachine

This comment has been minimized.

@elasticmachine

This comment has been minimized.

Follow-up to elastic#28497

Since elastic/elasticsearch#37285 has been merged, it's
aparent there are a couple more places we need to specify include_type_name
as a stop-gap until elastic#23650 is completed

Signed-off-by: Tyler Smalley <[email protected]>
Signed-off-by: Tyler Smalley <[email protected]>
@elasticmachine

This comment has been minimized.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@tylersmalley tylersmalley changed the title Use include_type_name when persisting ES data [migrations] Fetch additional mappings with types Jan 15, 2019
Copy link
Contributor

@chrisdavies chrisdavies left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Seems reasonable as a stopgap, but I think we need to follow up by removing this, and removing doc altogether from our calls to these. I can do that as part of my work on this: #23650

@chrisdavies chrisdavies merged commit 8d054a9 into elastic:master Jan 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Team:Operations Kibana-Operations Team v7.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants